Why even use Server when it is just about Serverless? cc @jasonkuhrt

Or is this the component name?

Heya,

So Nexus has a "server" component that can be either in serverful or serverless mode.

For example:

import { server } from 'nexus'

server.middleware() // ... this would work over serverless OR serverful

From a product POV this is still a WIP, we'll see how #782 goes + evolves...

To your question, the guides, it is not that the guide title was intended to match the component name. However, we felt that having two guides serverless and serverful would be confusing. Also a lot of content that applies to one applies to the other (e.g. middleware).

We wanted a single guide for all "server related stuff", and concluded on the name server. Within it, there will be three parts:

1. serverless only stuff
2. serverful only stuff
3. general stuff shared by all modes

Now that you have the context, do you have a suggestion for a better guide name?

I would write both Schema component and Server component:

Further down the nav they are referred to as components:

(is 'logging' also a 'logger component')?